GOALS: add accounts, Floodwall Cloud and operations tasks - #42

What this adds

Three new sections in GOALS.md, with the next tasks for the site and the product. Each task has a stable FW- id, a size (S, M, L, or a decision to make), and when to pick it up (now, next, later). No code changes.

Accounts, sign-in and billing (FW-601 to FW-610)

• Sign-in state in the site header: Sign in and Get started when signed out, the person's name and a menu when signed in.
• A profile name, since accounts store only an email today.
• Open sign-up (SIGNUP_MODE set to "open") with the waitlist wording changed, plus Cloudflare Turnstile so open sign-up can't be scripted to use up the Resend quota.
• Terms, Privacy and Refund pages. /signup already says signing up accepts the terms, and payment providers require them.
• Choosing a payment provider, then plans and checkout, with billing on /account.
• Account controls, sign in with GitHub and Google, and a welcome email.

Floodwall Cloud (FW-701 to FW-706)

• The console runs an example plane in the browser, and pricing charges per 1,000 decisions, so usage billing needs a real plane. These tasks cover a hosted plane per account (the crate compiled to WebAssembly on Cloudflare), API keys, a usage dashboard, usage-based billing, teams and roles (tied to FW-907), and alerts for held intents.

Site and operations (FW-801 to FW-804)

• Error alerts for the Worker and site, privacy-friendly analytics, docs and a quickstart, and a plan for releasing preview to floodwall.ai.

The same tasks are on the roadmap board. The suggested order is FW-603 with FW-604, then FW-601 and FW-602, then FW-605. FW-606 and FW-804 are decisions that can be made alongside them.

🤖 Generated with Claude Code